Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

OCTRL-899 [core] use SOSOR and EOEOR as run duration for GRP ECS object #590

Merged
merged 1 commit into from
Jul 16, 2024

Conversation

knopers8
Copy link
Collaborator

Ruben and Chiara need the O2 run duration in GRP ECS objects to be the narrowest timespan which includes CTP start and stop. Also start of run time should be ready available when the tasks are started. Because of these two reasons, we should use SOSOR and EOEOR as the timestamps in GRP ECS object.

@knopers8
Copy link
Collaborator Author

Keeping as WIP until #588 is merged.

Ruben and Chiara need the O2 run duration in GRP ECS objects to be the narrowest timespan which includes CTP start and stop.
Also start of run time should be ready available when the tasks are started.
Because of these two reasons, we should use SOSOR and EOEOR as the timestamps in GRP ECS object.
@knopers8 knopers8 changed the title WIP OCTRL-899 [core] use SOSOR and EOEOR as run duration for GRP ECS object OCTRL-899 [core] use SOSOR and EOEOR as run duration for GRP ECS object Jul 15, 2024
@knopers8
Copy link
Collaborator Author

I tested it on staging, it seems to be working as expected as long as AliceO2Group/ControlWorkflows#656 is also included.

@knopers8 knopers8 merged commit a88daa0 into AliceO2Group:master Jul 16, 2024
2 checks passed
@knopers8 knopers8 deleted the ccdb-grp-ecs-sosor-eoeor branch July 16, 2024 12:42
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

Successfully merging this pull request may close these issues.

2 participants